System for On-site Management of an Event

ABSTRACT

A method includes receiving, by a check-in device associated with the event management system, a ticket information for an attendee of an event, the check-in device comprising an access point, the access point being operable to connect by a wireless signal to one or more mobile devices, transmitting, from the check-in device to a gatekeeper system associated with the event management system, the ticket information for the attendee, wherein the gatekeeper system comprises a router, a switch, and a computing system, and wherein the check-in device is communicably connected to the gatekeeper system, validating, by the gatekeeper system, the ticket information for the attendee, and transmitting, from the gatekeeper system to the check-in device, an indication of validity of the ticket information for the attendee.

PRIORITY

This application is a continuation under 35 U.S.C. §120 of U.S. patentapplication Ser. No. 14/099,753, filed 6 Dec. 2013, which is acontinuation under 35 U.S.C. §120 of U.S. patent application Ser. No.13/773,005, filed 21 Feb. 2013, now issued as U.S. Pat. No. 8,608,054,which is a continuation under 35 U.S.C. §120 of U.S. patent applicationSer. No. 13/234,000, filed 15 Sep. 2011, now issued as U.S. Pat. No.8,397,984.

TECHNICAL FIELD

The present disclosure generally relates to event management systems andsystems for managing and monitoring ticket processing and attendeecheck-in at events.

BACKGROUND

Entry management at events is a long established problem. Typically,event organizers will have someone man the door equipped with aclipboard, a list of all the registered attendees printed on paper and apen to mark off those who have entered. The process is time consumingand breaks down when an event has multiple locations with multiplepoints of entry. Entry lines will often be long and slow as the personat the door looks up each person on the list. When multiple locationsare involved, a person could sneak into the event by giving the name ofa person that went in the other door. [4] Event management informationcan be stored in relational databases. Generally, a relational databaseis a collection of relations (frequently referred to as tables).Relational databases use a set of mathematical terms, which may useStructured Query Language (SQL) database terminology. MySQL is arelational database management system (RDBMS) that runs as a serverproviding multi-user access to a number of databases. SQLite is asoftware library that implements a self-contained, serverless,zero-configuration, transactional SQL database engine.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsfeatures and advantages, reference is now made to the followingdescription, taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 illustrates a system that provides on-site management ofspectator entry into an event;

FIG. 2 illustrates an example system for implementing an on-linegatekeeper system in order to provide on-site management of spectatorentry into an event;

FIG. 3 illustrates an example gatekeeper computing system of FIG. 1;

FIG. 4 illustrates an example mobile device of FIG. 1;

FIG. 5 illustrates an example event management system of FIG. 2;

FIG. 6 illustrates an example gatekeeper computing system of FIG. 1;

FIG. 7 illustrates an example gatekeeper system of FIG. 1;

FIG. 8 illustrates a method for setting up a system in order to provideon-site management of spectator entry into an event; and

FIG. 9 illustrates an example computer system.

DETAILED DESCRIPTION OF THE DRAWINGS

Embodiments of the present disclosure are best understood by referringto FIGS. 1 through 9 of the drawings, like numerals being used for likeand corresponding parts of the various drawings.

FIG. 1 illustrates a system 10 that provides on-site management ofspectator entry into an event. System 10 includes a gatekeeper system 14that may manage entry of spectators into an event by providing anindication of validity 42 for a ticket 72 presented by a spectatorattempting entry into the event. According to the illustratedembodiment, gatekeeper system 14 includes a protective casing 18 thatprotects gatekeeper system 14 from one or more conditions that may bepresent on-site at an event. In particular embodiments, protectivecasing 18 is a portable, ruggedized, and waterproof casing that houses arouter 22, a switch 26, an uninterrupted power supply 30, and agatekeeper computing system 38, each of which may assist gatekeepersystem 14 in providing the indication of validity 42 of the ticket 72presented by a spectator at the event. In particular embodiments, sinceprotective casing 18 is a portable, ruggedized, and waterproof casing,gatekeeper system 14 may be easily transported to an event, and set upto provide on-site management of spectator entry into the event withoutsubjecting the components of gatekeeper system 14 to the conditionson-site. In particular embodiments, since gatekeeper system 14 includeseach of router 22, switch 26, uninterrupted power supply 30, andgatekeeper computing system 38 (all housed in protective casing 18)gatekeeper system 14 may be easily transported to and set up on-site toprovide on-site management of spectator entry into an event.

As discussed above, gatekeeper system 14 provides the indication ofvalidity 46 of the ticket 74 presented by a spectator attempting toenter an event. An event may be, for example, a party, a concert, aconference, a sporting event, a fundraiser, a networking event, or alive performance. Although various event forums may have built-insystems for managing spectator entry into the event (such as footballstadiums), many events may occur in locations where a built-in systemfor managing spectator entry is unavailable. For example, some eventsmay occur in parking lots, open fields, fairgrounds, buildings thattypically do not host events, and/or other locations where a built-insystem for managing spectator entry is not available. Furthermore, manyof these locations may have conditions (such a little to no protectionfrom wind, rain, mud, etc.) that are unsuitable for electronic systems.In particular embodiments, gatekeeper system 14 may manage entry ofspectators into an event. Furthermore, gatekeeper system 14 may includea protective casing 18 that protects gatekeeper system 14 from one ormore conditions that may be present on-site at an event.

According to the illustrated embodiment, gatekeeper system 14 includesprotective casing 18, router 22, switch 26, uninterrupted power supply30, storage area 34, and gatekeeper computing system 38. In particularembodiments, gatekeeper system 14 may include any other components forproviding the indication of validity 46 of the ticket 74 presented by aspectator attempting entry at an event.

Protective casing 18 represents any components that may protectgatekeeper system 14 from one or more conditions that may be presenton-site at an event. In particular embodiments, protective casing 18 isa portable casing. As such, protective casing 18 (and any components ofgatekeeper system 14 located inside of protective casing 18) may beeasily transported to and from an event. In particular embodiments,protective casing 18 may be carried by three people or less. Inparticular embodiments, protective casing 18 is a ruggedized casing. Assuch, protective casing 18 (and any components of gatekeeper system 14located inside of protective casing 18) may be protected from roughhandling and accidents that may occur on-site at the event. For example,protective casing 18 may be accidentally dropped from small heights(such as less than 3 feet) without damaging (or substantially damaging)one or more components of gatekeeper system 14. In particularembodiments, protective casing 18 is a waterproof casing. As such,protective casing 18 (and any components of gatekeeper system 14 locatedinside of protective casing 18) may be protected from liquids (such aswater) and/or mixtures of liquids and solids (such as mud). Inparticular embodiments, protective casing 18 is a portable, ruggedized,and/or waterproof casing. [20] Protective casing 18 may be made of anymaterial type that allows it to be portable, ruggedized, and/orwaterproof. For example, protective casing 18 may be made out of apolypropylene copolymer material that is lightweight, durable and highlychemical resistant.

Router 22 represents any components that may join two or more wired orwireless networks together so as to route data between the networks.Router 22 may include any suitable router. For example, router 22 mayinclude a multi-wide area network (WAN) router. As such, router 22 mayload balance between various network connections so as to provideoptimum connectivity. In particular embodiments, router 22 may includeany router available from Peplink, such as the Peplink Balance 30, orany router available from any other router manufacturer or provider.

In particular embodiments, router 22 may couple gatekeeper system 14 toone or more networks so that ticket information stored on gatekeepercomputing system 38 may be updated from a master ticket information listfor the event, as is discussed in further detail in FIG. 2. Inparticular embodiments, this may allow gatekeeper computing system 38 tohave the most current information with regard to the event beingmanaged.

In particular embodiments, router 22 may connect to a WAN at theoperating site of the event (such as by connecting directly to a digitalsubscriber line (DSL) available at the operating site of the event). Inparticular embodiments, if a WAN is not available at the operating siteof the event, router 22 may connect to any suitable network (such asnetworks provided by a mobile router, a mobile WiFi device, and/or mediacenter bridges).

Router 22 may include any number of connection ports and any type ofconnection ports for joining two or more wired or wireless networkstogether. For example, router 22 may include Universal Serial Bus (USB)connection ports, Ethernet cabling connection ports (such as connectionports for category 5 cable), any other connection ports, or anycombination of the preceding. In particular embodiments, router 22 maybe located inside of protective casing 18. As such, router 22 may beprotected from the outside environment throughout its operation.

Switch 26 represents any components that join two or more computingsystems together into a single network. For example, switch 26 may jointwo or more computing systems together into a single local area network(LAN). In particular embodiments, switch 26 may include any type ofswitch. For example, switch 22 may include any switch available fromCisco Systems, Inc., such as the Cisco SF302-08P, or any switchavailable from any other switch manufacturer or provider.

In particular embodiments, switch 22 may be a power over Ethernet (POE)switch that may route both electrical power and data between multiplecomputing systems. According to the illustrated embodiment, switch 26connects access points 58 to gatekeeper computing system 38. As such,not only may switch 26 provide power for each access point 58 and alsofor gatekeeper computing system 38, but switch 26 may further route datapackets between access points 58 and gatekeeper computing system 38.

Switch 26 may include any number of connection ports and any type ofconnection ports for joining two or more computing systems together intoa single network. For example, switch 26 may include USB connectionports, Ethernet cabling connection ports (such as connection ports forcategory 5 cable), any other connection ports, or any combination of thepreceding. In particular embodiments, switch 26 may be located inside ofprotective casing 18. As such, switch 26 may be protected from theoutside environment throughout its operation.

Uninterrupted power supply 30 represents any components that may providepower to one or more components of system 10 if an input power source isunavailable. Uninterrupted power supply 30 may include any type ofuninterrupted power supply. For example, uninterrupted power supply 30may include any uninterrupted power supply available from APC, such asthe APC SC450RM1U, or any uninterrupted power supply available from anyother uninterrupted power supply manufacturer or provider.

In particular embodiments, uninterrupted power supply 30 may beconnected to an input power source at the operating site of the event.When the input power source is providing power, uninterrupted powersupply 30 may provide the power received from the power source to accesspoints 58 and/or components of gatekeeper system 14 (such as gatekeepercomputing system 38). In particular embodiments, such power may beprovided to access points 58 and gatekeeper computing system 38 thoughswitch 26. On the other hand, if a power source at the operating site ofthe event is unavailable or non-operational, uninterrupted power supply30 may supply power stored at uninterrupted power supply 30 to accesspoints 58 and/or components of gatekeeper system 14. In particularembodiments, uninterrupted power supply 30 may provide stored power forany amount of time. For example, uninterrupted power supply 30 mayprovide stored power for five minutes, ten minutes, one hour, two hours,four hours, eight hours, or any other amount of time. In particularembodiments, uninterrupted power supply 30 may keep each of the accesspoints 58 and the components of gatekeeper system 14 running for up tosix hours.

In particular embodiments, uninterrupted power supply 30 may be locatedinside of protective casing 18. As such, uninterrupted power supply 30may be protected from the outside environment throughout its operation.

Storage area 34 represents an area in protective casing 18 that maystore gatekeeper computing system 38 when gatekeeper computing system 38is not in use. For example, when gatekeeper computing system 38 is notoperating (such as when gatekeeper system 14 is not yet set up at aparticular event), gatekeeper computing system 38 may be stored instorage area 34. Thus, gatekeeper computing system 38 may be protectedby protective casing 18. In particular embodiments, prior to gatekeepercomputing system 38 being turned on for operation, gatekeeper computingsystem 38 may be removed from storage area 34 and connected togatekeeper system 14 (such as through switch 26).

Storage area 34 may have any suitable size and shape. For example,storage area 35 may store a gatekeeper computing system 38 of any size.Furthermore, although storage area 34 has been described as storinggatekeeper computing system 38, in particular embodiments, storage area34 may further store other components of gatekeeper system 14, such asone or more connectors that may be used to connect various devices togatekeeper system 14. Additionally, although gatekeeper computing system38 has been described as being stored in storage area 34 of protectivecasing 18, and removable from storage area 34 when gatekeeper computingsystem 38 is in operation, in particular embodiments, gatekeepercomputing system 38 may be located inside of protective casing 18 whilein operation, as is described in FIG. 7.

Gatekeeper computing system 38 represents any components that maydetermine the indication of validity 46 of ticket 74, and communicatethe indication of validity 46. Gatekeeper computing system 38 mayinclude any suitable computing device, such as, for example, a networkserver, any remote server, a mainframe, a host computer, a workstation,a personal computer, a laptop, a cellular phone, a smartphone, apersonal digital assistant, an ultra-mobile PC, or a computing tablet.Particular embodiments of gatekeeper computing system 38 are furtherdescribed in FIG. 3.

Indication of validity 46 may represent any indication regarding thevalidity of ticket 74. For example, indication of validity 46 mayindicate that ticket 74 is valid, and therefore the spectator that haspresented ticket 74 may be allowed to enter the event. In particularembodiments, indication of validity 46 may indicate that ticket 74 isinvalid and therefore the spectator that has presented ticket 74 may notbe allowed to enter the event. In addition to indicating the validity ofticket 74, indication of validity 46 may further provide furtherinformation regarding ticket 74. For example, indication of validity 46may further indicate that ticket 74 is valid but entry into the event isnot allowed at this time for ticket 74. For example, if certain ticketsallow for earlier entry into an event than other tickets, indication ofvalidity 76 may indicate that the ticket 74 is valid, but that entryusing the ticket 74 is not permitted at this time. As another example,indication of validity 46 may further indicate that although ticket 74is valid, ticket 74 may not be used at a particular entry location forthe event. For example, particular tickets may require that the ticketsbe presented at a particular gate. As such, if ticker 74 is presented atthe wrong gate, indication of validity 46 may indicate that althoughticket 74 is valid, it may not be used to enter at that particular gate.

According to the illustrated embodiment, gatekeeper computing system 38and access points 58 are connected to switch 26 of gatekeeper system 14by switch connectors 50. Switch connector 50 may represent any connectorthat connects a device to switch 26 so that switch 26 may provide dataand/or electrical power to the device. In particular embodiments, switchconnector 50 may be any type of connector. For example, switch connector50 may be a category 5 cable. In particular embodiments, switchconnector 50 may be rubberized so as to protect it from environmentsencountered at the event. In particular embodiments, switch connector 50may have any length so as to connect access points 58 (and/or otherdevices) to switch 26 over any distance.

Access point protective casing 54 represents any components that mayprotect access point 58 from one or more conditions that may be presenton-site at an event. In particular embodiments, access point protectivecasing 54 is a portable casing. As such, access point protective casing54 (and access point 54) may be easily transported to and from an event.In particular embodiments, access point protective casing 54 may becarried by one person. In particular embodiments, access pointprotective casing 54 is a ruggedized casing. As such, access pointprotective casing 54 (and access point 58) may be protected from roughhandling and accidents that may occur on-site at the event. For example,access point protective casing 54 may be accidentally dropped from smallheights (such as less than 3 feet) without damaging (or substantiallydamaging) access point 58. In particular embodiments, access pointprotective casing 54 is a waterproof casing. As such, access pointprotective casing 54 (and access point 58) may be protected from liquids(such as water) and/or mixtures of liquids and solids (such as mud). Inparticular embodiments, access point protective casing 54 is a portable,ruggedized, and/or waterproof casing.

Access point protective casing 54 may be made of any material type thatallows it to be portable, ruggedized, and/or waterproof. For example,access point protective casing 54 may be made out of a polypropylenecopolymer material that is lightweight, durable and highly chemicalresistant.

According to the illustrated embodiment, access points 58 are positionedwithin respective access point protective casings 54. Access point 58represents any components for receiving and transmitting radio signalsfor a wireless network. In particular embodiments, access point 58 mayreceive and transmit radio signals for a wireless local area network(WLAN). In particular embodiments, the WLAN may include WiFi, WiMax,BlueTooth, or other suitable standards. Access point 58 may be any typeof access point. For example, access point 58 may include any accesspoint available from Cisco Systems, Inc., such as the Cisco 1262 accesspoint, or any access point available from any other access pointmanufacturer or provider.

In particular embodiments, access point 58 may be a wireless accesspoint. In particular embodiments, access point 58 may receive and sendradio signals over any suitable distance. For example, access point 58may receive and send radio signals across a distance of over 80 feet ineach direction. As such, mobile device 70 may be located anywhere withinthe 80 feet distance from access point 58 and may still communicate withaccess point 58. [40] In particular embodiments, access point 58 may bea dual frequency access point. For example, access point 58 maybroadcast in two different frequencies, such as 5 GHz and 2.5 GHz. Inparticular embodiments, access point 58 may operate in accordance withany IEEE 802.11 WLAN standard, such as A, B, G, and/or N. In particularembodiments, access point 58 may receive data from mobile device 70 andtransmit the data to gatekeeper computing system 38. In particularembodiments, access point 58 may receive data from gatekeeper computingsystem 38 and transmit the data to mobile device 70.

In particular embodiments, access point 58 may be autonomous or aso-called “fat” wireless access point or a light-weight wireless accesspoint operating in connection with a wireless switch, such as switch 26.In addition, the network infrastructure may also include a Wireless LANSolution Engine (WLSE) offered by Cisco Systems, Inc. or anotherwireless network management system. In some implementations, the networkinfrastructure may also include one or more Wireless Control System(WCS) nodes operative to manage one or more wireless switches and accesspoints.

According to the illustrated embodiment, access point protective casing54 may further include connector 62. Connector 62 represents anyconnector (such as a clamp) that may connect access point protectivecasing 54 to a support structure. For example, in order for access point58 to better receive radio signals from mobile device 70, access pointprotective casing 54 (which includes access point 58) may be positionedoff the ground. As such, connector 62 may couple access point protectivecasing 54 to support structure 66 so as to hold access point protectivecasing 54 off the ground. In particular embodiments, connector 62 maycouple access point protective casing 54 to any suitable supportstructure. For example, connector 62 may couple access point protectivecasing 54 to a pole of a tent, a speaker stand, a fence, scaffolding,standard rigging, or any other support structure at the event.

In particular embodiments, access point protective casing 54 may furtherinclude any connection port for connecting access point 58 to switch 26.For example, access point protective casing 54 may include an Ethernetcard connection that is accessible from the outside of access pointprotective casing 54.

As is discussed above, access point 58 may receive and transmitcommunications to and from mobile device 70. Mobile device 70 representsany components that communicate with gatekeeper computing system 38 inorder to receive the indication of validity 46 of ticket 74. Mobiledevice 70 may include any suitable computing device, such as, forexample, a personal computer, a laptop, a cellular phone, a smartphone,a personal digital assistant, an ultra-mobile PC, or a computing tablet.In particular embodiments, mobile device 70 may include any mobiledevice available from Motorola, such as the Motorola Symbol MC65 2D, orany mobile device available from any other mobile device manufacturer orprovider. Particular embodiments of mobile device 70 are furtherdescribed in FIG. 4.

In particular embodiments, mobile device 70 may scan ticket identifier78 of ticket 74, and communicate the ticket identifier 78 to gatekeepercomputing system 38 in order to receive the indication of validity 46 ofticket 74. In particular embodiments, mobile device 70 may scan ticketidentifier 78 in any manner. For example, mobile device 70 may includeany suitable scanning device, such as, for example a camera, an opticalscanner, a barcode scanner, a QR code scanner, or any another scanningdevice. In particular embodiments, mobile device 70 may further includea display for displaying the indication of validity 46. As such, a userof mobile device 70 may allow the spectator to enter the event orprevent the spectator from entering the event. In particularembodiments, while mobile device 70 is operating in system 10, one ormore functionalities of mobile device 70 may be shut down. For example,mobile device 70 may only be able to perform functionalities related tothe event management (such as scanning).

Ticket 74 represents any object that may be used to gain access to theevent. According to the illustrated embodiment, ticket 74 includesticket identifier 78. Ticket identifier 78 includes any identifier thatmay be scanned by mobile device 70 in order to determine whether ticket74 is valid or not. In particular embodiments, ticket identifier 78 maybe an identification number, a barcode, a 2D barcode, a QR code, oranother suitable identifier. In particular embodiments, ticketidentifier 78 may be unique identifier.

In an example embodiment of operations, a spectator may desire to entera particular event. In order to do so, the spectator may present ticket74 to a user with mobile device 70. Mobile device 70 may scan ticketidentifier 78 from ticket 74 and transmit ticket identifier 78 togatekeeper computing system 38. Based on ticket identifier 78,gatekeeper computing system 38 may generate the indication of validity46 of ticket 74. Gatekeeper computing system 38 may then transmit theindication of validity 46 to mobile device 70 (via switch 26 and accesspoint 58 a) so that mobile device 70 may display the indication ofvalidity 46. For example, mobile device 70 may display an indication ofvalidity 46 that indicates that ticket 74 is valid. As such, the user ofmobile device 70 may allow the spectator with ticket 74 to enter theevent. In particular embodiments, since the components of gatekeepersystem 14 are protected by protective casing 18, such management ofspectator entry may occur on-site, even in poor conditions.

Modifications, additions, or omissions may be made to system 10 withoutdeparting from the scope of the invention. For example, gatekeepersystem 14 may include an access point 58 located in protective casing18. Additionally, system 10 may include any number of gatekeeper systems10 (and/or components of gatekeeper systems 10), access point protectivecases 18 (and/or access points 58), and/or mobile devices 70. Anysuitable logic may perform the functions of system 10 and the componentswithin system 10.

FIG. 2 illustrates an example system 100 for implementing an on-linegatekeeper system in order to provide on-site management of spectatorentry into an event. System 100 includes an event management system 82that is connected to gatekeeper systems 14 through network 86.Furthermore, system 100 also includes mobile devices 70 connected togatekeeper systems 14 through networks 90.

Event management system 82 represents any components that maycommunicate with gatekeeper computing system 38 of gatekeeper system 14in order to update ticket information stored on gatekeeper computingsystem 38 and further to update a master ticket information list storedon event management system 82. Event management system 82 may includeany suitable computing device, such as, for example, a network server,any remote server, a mainframe, a host computer, a workstation, apersonal computer, or a laptop.

In particular embodiments, event management system 82 may be anetwork-addressable computing system that can host one or more eventorganization and management systems. Event management system 82 maygenerate, store, receive, and transmit event-related data, such as, forexample, event listings, event details, event history details, eventregistration details, event organizer details, event attendee details,ticket purchase details, attendee check-in details, and event displays.Event management system 82 may be accessed by the other components ofsystem 100, either directly or via network 86. Particular embodiments ofevent management system 82 are further described in FIG. 5.

Network 86 may be any suitable communications network. As an example andnot by way of limitation, one or more portions of network 86 may includean ad hoc network, an intranet, an extranet, a virtual private network(VPN), a LAN, a WLAN, a wireless WAN (WWAN), a metropolitan area network(MAN), a portion of the Internet, a portion of the Public SwitchedTelephone Network (PSTN), a cellular telephone network, or a combinationof two or more of these. Network 86 may include one or more networks 86.According to the illustrated embodiment, network 86 may connectgatekeeper systems 14 to event management system 82.

As is discussed in FIG. 1, gatekeeper system 14 may provide theindication of validity 46 of the ticket 74 presented by a spectatorattempting to enter an event. As is illustrated, gatekeeper system 14includes gatekeeper computing system. Gatekeeper computing system 38represents any components that may determine the indication of validity46 of ticket 74, and communicate the indication of validity 46.Gatekeeper computing system 38 may include any suitable computingdevice, such as, for example, a network server, any remote server, amainframe, a host computer, a workstation, a personal computer, alaptop, a cellular phone, a smartphone, a personal digital assistant, anultra-mobile PC, or a computing tablet. Particular embodiments ofgatekeeper computing system 38 are further described in FIG. 3.

Network 90 may be any suitable communications network. As an example andnot by way of limitation, one or more portions of network 90 may includean ad hoc network, an intranet, an extranet, a VPN, a LAN, a WLAN, aWWAN, a MAN, a portion of the Internet, a portion of the PSTN, acellular telephone network, or a combination of two or more of these.Network 90 may include one or more networks 90. Furthermore, althoughnetwork 90 and network 86 are illustrated as different networks, inparticular embodiments, network 90 and network 86 may be the samenetwork. According to the illustrated embodiment, network 90 may connectmobile devices 70 to gatekeeper system 14.

As is discussed in FIG. 1, mobile device 70 represents any componentsthat communicate with gatekeeper computing system 38 in order to receivethe indication of validity 46 of ticket 74. Mobile device 70 may includeany suitable computing device, such as, for example, a personalcomputer, a laptop, a cellular phone, a smartphone, a personal digitalassistant, an ultra-mobile PC, or a computing tablet. In particularembodiments, mobile device 70 may include any mobile device availablefrom Motorola, such as the Motorola Symbol MC65 2D, or any mobile deviceavailable from any other mobile device manufacturer or provider.Particular embodiments of mobile device 70 are further described in FIG.4.

In an example embodiment of operations, event management system 82 mayinclude a master ticket information list (discussed in FIG. 5) for aparticular event. Once gatekeeper system 14 is connected to eventmanagement system 82 through network 86, event management system 82 maysend an initial message 100 to gatekeeper system 14. In particularembodiments, initial message 100 may include ticket information(discussed in FIG. 3) for the event. In particular embodiments, ticketinformation may be an exact copy of the master ticket information liststored at event management system 82. As such, by receiving initialmessage 100, gatekeeper computing system 38 of gatekeeper system 14 mayhave a list of all ticket identifiers 78 for the event. In particularembodiments once gatekeeper computing system 38 includes the ticketinformation, gatekeeper computing systems 38 may be able to provide anindication of validity 46 for each ticket 74. As such, spectators forthe event may be allowed to begin presenting tickets 74 for entry intothe event.

Once a spectator presents ticket 74 to a user of mobile device 70,mobile device 70 may scan ticket identifier 78 from ticket 74 andtransmit ticket identifier 78 to gatekeeper computing system 38 throughnetwork 90. Gatekeeper computing system 38 may then compare ticketidentifier 78 to the ticket information stored at gatekeeper computingsystem 38. Based on this comparison, gatekeeper computing system 38 maygenerate the indication of validity 46 of ticket 74, and transmit theindication of validity 46 to mobile device 70.

In addition to generating the indication of validity 46, gatekeepercomputing system 38 may further update the ticket information stored ongatekeeper computing system 38 based on the comparison between thestored information and the ticket identifier 78. For example, based onthe comparison, gatekeeper computing system 38 may determine that aparticular ticket identifier 78 has been scanned, and therefore mayupdate the ticket information to indicate that the particular ticketidentifier 78 has been scanned and may no longer be used to allow anyother spectators to enter the event. As such, if another spectatorattempts to enter the event with a ticket 74 with that same ticketidentifier 78, gatekeeper computing system 38 may determine that theparticular ticket identifier 78 has already been used, and may providean indication of validity 46 that indicates that the ticket is notvalid. Thus, the spectator may be prevented from entering the event.

In particular embodiments, while gatekeeper computing system 38 isproviding on-site management of spectator entry into the event,gatekeeper computing system 38 may further transmit ticketidentification message 104 to event management system 82 through network86. In particular embodiments, ticket indication message 104 may includeany information that may cause event management system 82 to update themaster ticket information list stored on event management system 82. Forexample, ticket indication message 104 may include an indication that aparticular ticket identifier 78 has been scanned by a mobile device 70and transmitted to gatekeeper computing system 38. As such, eventmanagement system 82 may update the master ticket information list toindicate that the particular ticket identifier 78 is no longer valid.Therefore, event management system 82 may have a master ticketinformation list that is kept up to date with the transactions occurringon-site.

In particular embodiments, gatekeeper computing system 38 may transmitticket indication message 104 at any time. For example, ticketindication message 104 may be transmitted to event management system 82each time gatekeeper computing system receives ticket identifier 78 andcompares that ticket identifier 78 to the ticket information stored ongatekeeper computing system 38. As such, each ticket indication message104 may only include a single ticket identifier 78.

In particular embodiments, gatekeeper computing system 38 may transmitticket indication message 104 to event management system 82periodically. For example, gatekeeper computing system 38 may transmitticket indication message 104 to event management system 82 every fewseconds, every few minutes, every few hours, or after any other amountof time. In particular embodiments, when the ticket indication message104 is transmitted periodically, the ticket indication message 104 mayinclude more than just a single ticket identifier 78. For example,ticket indication message 104 may include one or more of the ticketidentifiers 78 that have been scanned and transmitted to gatekeepercomputing system 38 since the last time gatekeeper computing system 38transmitted ticket indication message 104 to event management system 82.In particular embodiments, ticket indication message 104 may include allof the ticket information stored at gatekeeper computing system 38 ormay only include an update (such as all of the new information that hasbeen added to the ticket information stored at gatekeeper computingsystem 38 since the last ticket indication message 104 was sent to eventmanagement system 82).

In particular embodiments, event management system 82 may periodicallytransmit an update message 108 to gatekeeper computing system 38. Updatemessage 108 may include any indication of one or more changes to themaster ticket information list that have occurred since initial message100 or the last update message 108. In particular embodiments, eventmanagement system 82 may transmit update message 108 every few seconds,every few minutes, every few hours, or after any other amount of time.

In particular embodiments, by receiving update message 108, gatekeepercomputing system may be able to update the ticket information stored atgatekeeper computing system 38 to match the master ticket informationlist stored at event management system 82. In particular embodiments,this may allow gatekeeper computing system 38 to have the most currentticket information. Therefore, if gatekeeper computing system 38 b hasreceived a particular ticket identifier 78 from mobile device 70 b,information regarding that particular ticket identifier 78 may betransmitted to event management system 82, and further transmitted togatekeeper computing system 38 a. As such, if a spectator attempts toenter the event with a ticket 74 that includes the exact same ticketidentifier 78 that was already scanned and transmitted to gatekeepercomputing system 38 b, the ticket information at gatekeeper computingsystem 38 a may include information that indicates that this particularticket identifier 78 has already been used for entry. As such,gatekeeper computing system 38 a may provide an indication of validity46 that indicates that the ticket identifier 78 is not valid.

Although system 100 illustrates gatekeeper computing system 38 receivingupdate messages 108 from event management system 82, in particularembodiments, gatekeeper computing system 38 may be unable to connect toevent management system 82 (such as when there is no internetconnectivity at the event). In such an embodiment, gatekeeper computingsystem 38 may still include the stored ticket information. As such,gatekeeper computing system 38 may still provide on-site management ofspectator entry into the event even when gatekeeper computing system 38is unable to connect to event management 82.

Modifications, additions, or omissions may be made to system 100 withoutdeparting from the scope of the invention. For example, although system100 illustrates a particular arrangement of event management system 82,network 86, gatekeeper systems 14, networks 90, and mobile devices 70,this disclosure contemplates any suitable arrangement of eventmanagement system 82, network 86, gatekeeper systems 14, networks 90,and mobile devices 70. As an example and not by way of limitation, twoor more of gatekeeper systems 14 may be connected to each otherdirectly, bypassing network 90 and event management system 82.Additionally, system 100 may include any suitable number of eventmanagement systems 82, networks 86, gatekeeper systems 14, networks 90,and/or mobile devices 70. Furthermore, any suitable logic may performthe functions of system 100 and the components within system 100.

Additionally, although system 100 illustrates update messages 108 beingtransmitted from event management system 82, in particular, updatemessages 108 may be transmitted directly from gatekeeper computingsystem 38 b to gatekeeper computing system 38 a, or vice versa.Furthermore, although system 100 illustrates initial message 100 beingreceived at gatekeeper computing system 38 through network 86, inparticular embodiments, initial message 100 (and/or the ticketinformation) may be received at gatekeeper computing system 38 in anyother manner.

FIG. 3 illustrates an example gatekeeper computing system 38 of FIG. 1.Gatekeeper computing system 38 represents any components that maydetermine the indication of validity 46 of ticket 74, and communicatethe indication of validity 46. Gatekeeper computing system 38 mayinclude any suitable computing device, such as, for example, a networkserver, any remote server, a mainframe, a host computer, a workstation,a personal computer, a laptop, a cellular phone, a smartphone, apersonal digital assistant, an ultra-mobile PC, or a computing tablet.In the illustrated embodiment, gatekeeper computing system 38 includes anetwork interface 112, a processor 116, and a memory 120.

Network interface 112 represents any device operable to receiveinformation from a network (such as network 86 and/or network 90 of FIG.2), transmit information through the network, perform processing ofinformation, communicate to other devices, or any combination of thepreceding. For example, network interface 112 receives ticket identifier78 from mobile device 70. As another example, network interface 112communicates the indication of validity 46 to mobile device 70. Networkinterface 112 represents any port or connection, real or virtual,including any suitable hardware and/or software, including protocolconversion and data processing capabilities, to communicate through aLAN, a MAN, a WAN, or other communication system that allows gatekeepercomputing system 38 to exchange information with the network, mobiledevices 70, event management system 82, other components of system 10 ofFIG. 1, or other components of system 100 of FIG. 2.

Processor 116 communicatively couples to network interface 112 andmemory 120, and controls the operation and administration of gatekeepercomputing system 38 by processing information received from networkinterface 112 and memory 120. Processor 116 includes any hardware and/orsoftware that operates to control and process information. For example,processor 116 executes application 124 to control the operation ofgatekeeper computing system 38. Processor 116 may be a programmablelogic device, a microcontroller, a microprocessor, any processingdevice, or any combination of the preceding.

Memory 120 stores, either permanently or temporarily, data, operationalsoftware, or other information for processor 116. Memory 120 includesany one or a combination of volatile or non-volatile local or remotedevices suitable for storing information. For example, memory 120 mayinclude random access memory (RAM), read only memory (ROM), magneticstorage devices, optical storage devices, or any other informationstorage device or a combination of these devices. While illustrated asincluding particular modules, memory 120 may include any information foruse in the operation of gatekeeper computing system 38.

In the illustrated embodiment, memory 120 includes application 124 andticket information 128. Application 124 represents any suitable set ofinstructions, logic, or code embodied in a computer-readable storagemedium and operable to facilitate the operation of gatekeeper computingsystem 38.

Ticket information 128 represents any information regarding tickets forthe event. For example, ticket information 128 includes a list of ticketidentifiers 78 that are valid, a list of ticket identifiers 78 that arenot valid, any other information that may be used to manage entry of oneor more spectators to the event, or any combination of the preceding. Inparticular embodiments, when gatekeeper computing system 38 receives aparticular ticket identifier 78 from mobile device 70, gatekeepercomputing system 38 may access ticket information 128 in order tocompare ticket information 128 to the ticket identifier 78. Inparticular embodiments, if the ticket information 128 indicates that theticket identifier 78 is valid (such as by determining that ticketidentifier 78 was listed as a valid ticket identifier 78), gatekeepercomputing system 38 may generate an indication of validity 46 thatindicates that ticket 74 is valid.

In particular embodiments, ticket information 128 may further includemobile device setting information. For example, as is discussed above,certain tickets may be given a priority over other tickets. As anexample, a higher priced ticket may allow a spectator to enter the eventearlier, or from a different gate than lower priced tickets. Inparticular embodiments, mobile device setting information may includeinformation that indicates which tickets 74 are allowed to be used atparticular mobile devices 70. For example, if a particular mobile device70 is being used at Gate A (which is a gate that may only be accessed byspectators with a ticket 74 that has a Gate A priority), mobile devicesetting information may include information that indicates that theparticular mobile device 70 can only allow entry to spectators thatinclude a ticket 74 with the Gate A priority. As such, if mobile device70 scans a ticket identifier 78 of a ticket 74 that does not include aGate A priority, gatekeeper computing system 38 may transmit anindication of validity 46 to mobile device 70 that indicates that theticket 74 is valid, but not at that gate. The user of mobile device 70may then direct the spectator to attempt entry to the event at anothergate.

In particular embodiments, ticket information 128 may further includeinformation regarding event attendees. For example ticket information128 may include information describing one or more of the attendeesregistered to attend the event, include the attendee's name, phonenumber, mailing address, email address, payment information, ticketorder information, ticket information, check-in status, and othersuitable attendee information.

FIG. 4 illustrates an example mobile device 70 of FIG. 1. Mobile device70 represents any components that communicate with gatekeeper computingsystem 38 in order to receive the indication of validity 46 of ticket74. Mobile device 70 may include any suitable computing device, such as,for example, a personal computer, a laptop, a cellular phone, asmartphone, a personal digital assistant, an ultra-mobile PC, or acomputing tablet. In particular embodiments, mobile device 70 mayinclude any mobile device available from Motorola, such as the MotorolaSymbol MC65 2D, or any mobile device available from any other mobiledevice manufacturer or provider. In the illustrated embodiment, mobiledevice 70 includes a network interface 140, a processor 144, and amemory 148.

Network interface 140 represents any device operable to receiveinformation from a network (such as network 90 of FIG. 2), transmitinformation through the network, perform processing of information,communicate to other devices, or any combination of the preceding. Forexample, network interface 140 communicates ticket identifier 78 togatekeeper computing system 38. As another example, network interface140 receives the indication of validity 46 from gatekeeper computingsystem 38. Network interface 140 represents any port or connection, realor virtual, including any suitable hardware and/or software, includingprotocol conversion and data processing capabilities, to communicatethrough a LAN, a MAN, a WAN, or other communication system that allowsmobile device 70 to exchange information with the network, gatekeepercomputing system 38, other components of system 10 of FIG. 1, or othercomponents of system 100 of FIG. 2.

Processor 144 communicatively couples to network interface 140 andmemory 148, and controls the operation and administration of mobiledevice 70 by processing information received from network interface 140and memory 148. Processor 144 includes any hardware and/or software thatoperates to control and process information. For example, processor 144executes application 152 to control the operation of mobile device 70.Processor 144 may be a programmable logic device, a microcontroller, amicroprocessor, any processing device, or any combination of thepreceding.

Memory 148 stores, either permanently or temporarily, data, operationalsoftware, or other information for processor 144. Memory 148 includesany one or a combination of volatile or non-volatile local or remotedevices suitable for storing information. For example, memory 148 mayinclude RAM, ROM, magnetic storage devices, optical storage devices, orany other information storage device or a combination of these devices.While illustrated as including particular modules, memory 148 mayinclude any information for use in the operation of mobile device 70.

In the illustrated embodiment, memory 148 includes application 152 andstatus indicators 156. Application 152 represents any suitable set ofinstructions, logic, or code embodied in a computer-readable storagemedium and operable to facilitate the operation of mobile device 70.

Status indicators 156 represent any information regarding the status ofmobile device 70. For example, status indicators 156 may include abattery level of mobile device 70, a wireless connection signal ofmobile device 70, scanning problem indications at mobile device 70 (suchas the user of mobile device 70 improperly scanning ticket identifier 78or the number of tickets 74 that have been presented at the wrong mobiledevice 70), any other status indicators of mobile device 70, or anycombination of the preceding. In particular embodiments, mobile device70 may retrieve status indicators 156 by monitoring the status of mobiledevice 70 in any manner. In particular embodiments, mobile device 70 maytransmit status indicators 156 to gatekeeper computing system 38.

FIG. 5 illustrates an example event management system 82 of FIG. 2.Event management system 82 represents any components that maycommunicate with gatekeeper computing system 38 in order to updateticket information stored on gatekeeper computing system 38 and furtherto update a master ticket information list stored on event managementsystem 82. Event management system 82 may include any suitable computingdevice, such as, for example, a network server, any remote server, amainframe, a host computer, a workstation, a personal computer, or alaptop. In the illustrated embodiment, event management system 82includes a network interface 180, a processor 184, and a memory 188.

Network interface 180 represents any device operable to receiveinformation from a network (such as network 86 of FIG. 2), transmitinformation through the network, perform processing of information,communicate to other devices, or any combination of the preceding. Forexample, network interface 180 communicates initial message 100 togatekeeper computing system 38. As another example, network interface180 receives ticket indication message 104 from gatekeeper computingsystem 38. Network interface 180 represents any port or connection, realor virtual, including any suitable hardware and/or software, includingprotocol conversion and data processing capabilities, to communicatethrough a LAN, a MAN, a WAN, or other communication system that allowsevent management system 82 to exchange information with the network,gatekeeper computing system 38, other components of system 10 of FIG. 1,or other components of system 100 of FIG. 2.

Processor 184 communicatively couples to network interface 180 andmemory 188, and controls the operation and administration of eventmanagement system 82 by processing information received from networkinterface 180 and memory 188. Processor 184 includes any hardware and/orsoftware that operates to control and process information. For example,processor 184 executes application 192 to control the operation of eventmanagement system 82. Processor 184 may be a programmable logic device,a microcontroller, a microprocessor, any processing device, or anycombination of the preceding.

Memory 188 stores, either permanently or temporarily, data, operationalsoftware, or other information for processor 184. Memory 188 includesany one or a combination of volatile or non-volatile local or remotedevices suitable for storing information. For example, memory 188 mayinclude RAM, ROM, magnetic storage devices, optical storage devices, orany other information storage device or a combination of these devices.While illustrated as including particular modules, memory 188 mayinclude any information for use in the operation of event managementsystem 82.

In the illustrated embodiment, memory 188 includes application 192 andmaster ticket information list 196. Application 192 represents anysuitable set of instructions, logic, or code embodied in acomputer-readable storage medium and operable to facilitate theoperation of event management system 82.

Master ticket information list 196 represents any information regardingtickets for the event. For example, master ticket information list 196includes a list of ticket identifiers 78 that are valid, a list ofticket identifiers 78 that are not valid, any other information that maybe used to manage entry of one or more spectators to the event, or anycombination of the preceding. In particular embodiments, master ticketinformation list 196 is a master list of all the information regardingtickets for the events. As such, if ticket information 128 stored atgatekeeper computing system 38 is lost or corrupted, master ticketinformation list 196 may be used to proved new ticket information 128 togatekeeper computing system 38. Furthermore, if any changes occur thataffect tickets for the event (such as the purchase of additional tickets74 or the invalidity of certain ticket identifiers 78), the changes maybe added to master ticket information list 196. The changes may then besent to gatekeeper computing systems 38 in order to update ticketinformation 128.

In particular embodiments, master ticket information list 196 mayfurther include any of the information included in ticket information128 stored at gatekeeper computing systems 38. For example, masterticket information list 196 may further include mobile device settinginformation (discussed above) and information regarding event attendees(also discussed above).

FIG. 6 illustrates an example gatekeeper computing system 38 of FIG. 1.According to the illustrated embodiment, gatekeeper computing system 38includes a display that displays indicator information 200 for mobiledevice 70. In particular embodiments, indicator information 200 includesa graphical display of the battery power of mobile device 70, the signalstrength of mobile device 70, and the number of improper scans conductedat mobile device 70. In particular embodiment, indicator information 200may further include a graphical display of the number of ticketidentifiers that have been scanned, the number of spectators that havebeen allowed and/or denied entry, the number of duplicate scans, thenumber of wrong gate scans, the number of refunded scans, and/or thetime and date of the last scan conducted at mobile device 70. Inparticular embodiments, indicator information 200 may be displayed bygatekeeper computing system 38 based on status indicators 156 receivedby the mobile device 70.

FIG. 7 illustrates an example of gatekeeper system 14 of FIG. 1. Inparticular embodiments, gatekeeper system 14 of FIG. 7 may be analternative embodiment of gatekeeper system 14 of FIG. 1. According tothe illustrated embodiment, and similar to gatekeeper system 14 of FIG.1, gatekeeper system 14 of FIG. 7 includes protective casing 18, router22, switch 26, uninterrupted power supply 30, storage area 34, andgatekeeper computing system 38. Unlike gatekeeper system 14 of FIG. 1,however, gatekeeper system 14 of FIG. 7 may include a gatekeepercomputing system 38 that is located inside of protective casing 18 whilein operation. As such, gatekeeper computing system 38 may be protectedfrom the outside environment throughout its operation.

In particular embodiments, since gatekeeper computing system 38 islocated inside of protective casing 18 while in operation, gatekeepercomputing system 38 may not include one or more user interfaces (such asone or more of a display, a keyboard, and/or a mouse). Despite nothaving one or more user interfaces, gatekeeper computing system 38 maystill determine the indication of validity 46 of ticket 74, andcommunicate the indication of validity 46 to a mobile device 70.

In particular embodiments, since gatekeeper computing system 38 may nothave one or more user interfaces, a user of gatekeeper system 14 may beable to connect to gatekeeper computing system 38 (such as throughnetwork 86 or network 90 of FIG. 2) in order to view a graphical userinterface that includes the status of the event (such as the indicationsof validity 46) and one or more viewable displays provided by gatekeepercomputing system 38 (such as indicator information 200 of FIG. 6).

FIG. 8 illustrates a method 400 for setting up a system in order toprovide on-site management of spectator entry into an event. Inparticular embodiments, one or more steps of method 400 may be performedusing gatekeeper system 14, access points 58, mobile device 70 and/orevent management system 82. The method begins at step 402. At step 404,the gatekeeper system (which is located in the protective casing) isdelivered to the event. In particular embodiments, the gatekeeper systemmay be delivered to the event by carrying the protective casing to theevent and setting it down at an operational point at the event.

At step 406, the protective casing is opened. In particular embodiments,the protective casing may be opened by opening a lid of the protectivecasing. In particular embodiments, the protective casing may be openedin order to access one or more components of the gatekeeper system. Inparticular embodiments, even when the lid of the protective casing isopen, the protective casing may still provide protection to one or morecomponents of the gatekeeper system.

At step 408, the gatekeeper system is plugged in. In particularembodiments, the gatekeeper system may be plugged into a network port inorder to connect the router of the gatekeeper system to a WAN or a LAN.In particular embodiments, the gatekeeper system may be plugged in byconnecting the gatekeeper system to a power source that provideselectrical power to the uninterrupted power supply of the gatekeepersystem.

At step 410, each access point is set up. In particular embodiments,each access point may be set up by connecting a switch connector (suchas a category 5 cable) to the switch of the gatekeeper system, andrunning the switch connector to the location where the access point willbe positioned. In particular embodiments, setting up each access pointmay further include coupling each access point to a support structure(such as a pole, speaker stand, fence, or scaffolding) by the connector.

At step 412, the gatekeeper system is powered on. In particularembodiments, the gatekeeper system may be powered on by turning on eachcomponent of the gatekeeper system. For example, each of the router,switch, uninterrupted power supply, and gatekeeper computing system maybe turned on. In particular embodiments, turning on the gatekeepercomputing system may include re-setting the ticket information stored onthe gatekeeper computing system and accessing the event managementsystem in order to pull down new ticket information for storage at thegatekeeper computing system (such as by receiving initial message 100 ofFIG. 2). In particular embodiments, this may allow the gatekeepercomputing system to have a local copy of the ticket information so thatthe gatekeeper computing system may provide on-site management ofspectator entry into the event even when the gatekeeper system is notconnected to the event management system. In particular embodiments, thegatekeeper computing system may already be pre-configured to include theticket information for the event. As such, the gatekeeper computingsystem may not need to pull down the new ticket information.

At step 414, each mobile device is powered on. In particularembodiments, each mobile device may be powered on by turning on eachmobile device.

At step 416, a gatekeeper system for each mobile device is selected. Inparticular embodiments, the gatekeeper system for each mobile device maybe selected by selecting the IP address for the gatekeeper system. Inparticular embodiments, since more than one gatekeeper system may beused at each event, the mobile device may need to choose whichgatekeeper system it will connect to in order to receive an indicationof validity for each scanned ticket. In particular embodiments, the IPaddress for each gatekeeper system may be hardcoded into each mobiledevice. As such, selecting the gatekeeper system may include selectingone of the gatekeeper systems that is displayed on the display of themobile device. In particular embodiments, the IP address for thegatekeeper systems may not be hardcoded into the mobile device. As such,the IP address for the selected gatekeeper system may be entered intothe mobile device in any manner. For example, a user of the mobiledevice may type in the IP address for the gatekeeper system. As anotherexample, each gatekeeper system may include a scannable identifier onthe gatekeeper system (such as a bar code printed on the protectivecasing of the gatekeeper system). As such, the gatekeeper system may beselected for the mobile device by scanning the identifier using themobile device.

Once a gatekeeper system has been selected for each mobile device, themethod moves to step 418 where the mobile device setting information isconfigured. In particular embodiments, configuring the mobile devicesetting information may include indicating what tickets each mobiledevice is allowed to scan. In particular embodiments, configuring themobile device setting information may include accessing the mobiledevice information stored in the gatekeeper computing system, andconfiguring the mobile device setting information in any manner. Forexample, the mobile device setting information for a first mobile devicemay be configured to only allow the first mobile device to scan ticketswith a Gate A priority. Additionally, the mobile device settinginformation for a second mobile device may be configured to allow thesecond mobile device to scan any of the tickets.

At step 420, on-site management of spectator entry into an event isprovided. In particular embodiments, providing such on-site managementmay include scanning a ticket identifier of a ticket and transmittingthe ticket identifier to the gatekeeper computing system. In particularembodiments, providing on-site management may further include comparingthe ticket identifier with the ticket information stored at thegatekeeper computing system, generating an indication of validity of theticket, and transmitting the indication of validity to the mobiledevice, so that the user of the mobile device may allow or deny entry tothat spectator. In particular embodiments, providing on-site managementmay further include updating the stored ticket information on thegatekeeper computing system based on the comparison, transmitting ticketindications to the event management system so that the event managementsystem may update the master ticket information list, and receivingupdate messages from the event management system so that the gatekeepercomputing system may keep an updated ticket information.

After on-site management of spectator entry into the event is provided,the method moves to step 422, where the method ends.

Modifications, additions, or omissions may be made to method 400. Forexample, one or more steps in method 400 in FIG. 8 may be performed inparallel or in any suitable order.

FIG. 9 illustrates an example computer system 500. In particularembodiments, one or more computer systems 500 perform one or more stepsof one or more methods described or illustrated herein. In particularembodiments, one or more computer systems 500 provide functionalitydescribed or illustrated herein. For example, computer system 500 may bean example of gatekeeper computing system 38, mobile device 70, and/orevent management system 82. In particular embodiments, software runningon one or more computer systems 500 performs one or more steps of one ormore methods described or illustrated herein or provides functionalitydescribed or illustrated herein. Particular embodiments include one ormore portions of one or more computer systems 500.

This disclosure contemplates any suitable number of computer systems500. This disclosure contemplates computer system 500 taking anysuitable physical form. As example and not by way of limitation,computer system 500 may be an embedded computer system, a system-on-chip(SOC), a single-board computer system (SBC) (such as, for example, acomputer-on-module (COM) or system-on-module (SOM)), a desktop computersystem, a laptop or notebook computer system, an interactive kiosk, amainframe, a mesh of computer systems, a mobile telephone, a personaldigital assistant (PDA), a server, a tablet computer system, or acombination of two or more of these. Where appropriate, computer system500 may include one or more computer systems 500; be unitary ordistributed; span multiple locations; span multiple machines; spanmultiple data centers; or reside in a cloud, which may include one ormore cloud components in one or more networks. Where appropriate, one ormore computer systems 500 may perform without substantial spatial ortemporal limitation one or more steps of one or more methods describedor illustrated herein. As an example and not by way of limitation, oneor more computer systems 500 may perform in real time or in batch modeone or more steps of one or more methods described or illustratedherein. One or more computer systems 500 may perform at different timesor at different locations one or more steps of one or more methodsdescribed or illustrated herein, where appropriate.

In particular embodiments, computer system 500 includes a processor 502,memory 504, storage 506, an input/output (I/O) interface 508, acommunication interface 510, and a bus 512. Although this disclosuredescribes and illustrates a particular computer system having aparticular number of particular components in a particular arrangement,this disclosure contemplates any suitable computer system having anysuitable number of any suitable components in any suitable arrangement.

In particular embodiments, processor 502 includes hardware for executinginstructions, such as those making up a computer program. As an exampleand not by way of limitation, to execute instructions, processor 502 mayretrieve (or fetch) the instructions from an internal register, aninternal cache, memory 504, or storage 506; decode and execute them; andthen write one or more results to an internal register, an internalcache, memory 504, or storage 506. In particular embodiments, processor502 may include one or more internal caches for data, instructions, oraddresses. This disclosure contemplates processor 502 including anysuitable number of any suitable internal caches, where appropriate. Asan example and not by way of limitation, processor 502 may include oneor more instruction caches, one or more data caches, and one or moretranslation lookaside buffers (TLBs). Instructions in the instructioncaches may be copies of instructions in memory 504 or storage 506, andthe instruction caches may speed up retrieval of those instructions byprocessor 502. Data in the data caches may be copies of data in memory504 or storage 506 for instructions executing at processor 502 tooperate on; the results of previous instructions executed at processor502 for access by subsequent instructions executing at processor 502 orfor writing to memory 504 or storage 506; or other suitable data. Thedata caches may speed up read or write operations by processor 502. TheTLBs may speed up virtual-address translation for processor 502. Inparticular embodiments, processor 502 may include one or more internalregisters for data, instructions, or addresses. This disclosurecontemplates processor 502 including any suitable number of any suitableinternal registers, where appropriate. Where appropriate, processor 502may include one or more arithmetic logic units (ALUs); be a multi-coreprocessor; or include one or more processors 502. Although thisdisclosure describes and illustrates a particular processor, thisdisclosure contemplates any suitable processor.

In particular embodiments, memory 504 includes main memory for storinginstructions for processor 502 to execute or data for processor 502 tooperate on. As an example and not by way of limitation, computer system500 may load instructions from storage 506 or another source (such as,for example, another computer system 500) to memory 504. Processor 502may then load the instructions from memory 504 to an internal registeror internal cache. To execute the instructions, processor 502 mayretrieve the instructions from the internal register or internal cacheand decode them. During or after execution of the instructions,processor 502 may write one or more results (which may be intermediateor final results) to the internal register or internal cache. Processor502 may then write one or more of those results to memory 504. Inparticular embodiments, processor 502 executes only instructions in oneor more internal registers or internal caches or in memory 504 (asopposed to storage 506 or elsewhere) and operates only on data in one ormore internal registers or internal caches or in memory 504 (as opposedto storage 506 or elsewhere). One or more memory buses (which may eachinclude an address bus and a data bus) may couple processor 502 tomemory 504. Bus 512 may include one or more memory buses, as describedbelow. In particular embodiments, one or more memory management units(MMUs) reside between processor 502 and memory 504 and facilitateaccesses to memory 504 requested by processor 502. In particularembodiments, memory 504 includes random access memory (RAM). This RAMmay be volatile memory, where appropriate Where appropriate, this RAMmay be dynamic RAM (DRAM) or static RAM (SRAM). Moreover, whereappropriate, this RAM may be single-ported or multi-ported RAM. Thisdisclosure contemplates any suitable RAM. Memory 504 may include one ormore memories 504, where appropriate. Although this disclosure describesand illustrates particular memory, this disclosure contemplates anysuitable memory.

In particular embodiments, storage 506 includes mass storage for data orinstructions. As an example and not by way of limitation, storage 506may include an HDD, a floppy disk drive, flash memory, an optical disc,a magneto-optical disc, magnetic tape, or a Universal Serial Bus (USB)drive or a combination of two or more of these. Storage 506 may includeremovable or non-removable (or fixed) media, where appropriate. Storage506 may be internal or external to computer system 500, whereappropriate. In particular embodiments, storage 506 is non-volatile,solid-state memory. In particular embodiments, storage 506 includesread-only memory (ROM). Where appropriate, this ROM may bemask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM),electrically erasable PROM (EEPROM), electrically alterable ROM (EAROM),or flash memory or a combination of two or more of these. Thisdisclosure contemplates mass storage 506 taking any suitable physicalform. Storage 506 may include one or more storage control unitsfacilitating communication between processor 502 and storage 506, whereappropriate. Where appropriate, storage 506 may include one or morestorages 506. Although this disclosure describes and illustratesparticular storage, this disclosure contemplates any suitable storage.

In particular embodiments, I/O interface 508 includes hardware,software, or both providing one or more interfaces for communicationbetween computer system 500 and one or more I/O devices. Computer system500 may include one or more of these I/O devices, where appropriate. Oneor more of these I/O devices may enable communication between a personand computer system 500. As an example and not by way of limitation, anI/O device may include a keyboard, keypad, microphone, monitor, mouse,printer, scanner, speaker, still camera, stylus, tablet, touchscreen,trackball, video camera, another suitable I/O device or a combination oftwo or more of these. An I/O device may include one or more sensors.This disclosure contemplates any suitable I/O devices and any suitableI/O interfaces 508 for them. Where appropriate, I/O interface 508 mayinclude one or more device or software drivers enabling processor 502 todrive one or more of these I/O devices. I/O interface 508 may includeone or more I/O interfaces 508, where appropriate. Although thisdisclosure describes and illustrates a particular I/O interface, thisdisclosure contemplates any suitable I/O interface.

In particular embodiments, communication interface 510 includeshardware, software, or both providing one or more interfaces forcommunication (such as, for example, packet-based communication) betweencomputer system 500 and one or more other computer systems 500 or one ormore networks. As an example and not by way of limitation, communicationinterface 510 may include a network interface controller (NIC) ornetwork adapter for communicating with an Ethernet or other wire-basednetwork or a wireless NIC (WNIC) or wireless adapter for communicatingwith a wireless network, such as a WI-FI network. This disclosurecontemplates any suitable network and any suitable communicationinterface 510 for it. As an example and not by way of limitation,computer system 500 may communicate with an ad hoc network, a personalarea network (PAN), a local area network (LAN), a wide area network(WAN), a metropolitan area network (MAN), or one or more portions of theInternet or a combination of two or more of these. One or more portionsof one or more of these networks may be wired or wireless. As anexample, computer system 500 may communicate with a wireless PAN (WPAN)(such as, for example, a BLUETOOTH WPAN), a WI-FI network, a WI-MAXnetwork, a cellular telephone network (such as, for example, a GlobalSystem for Mobile Communications (GSM) network), or other suitablewireless network or a combination of two or more of these. Computersystem 500 may include any suitable communication interface 510 for anyof these networks, where appropriate. Communication interface 510 mayinclude one or more communication interfaces 510, where appropriate.Although this disclosure describes and illustrates a particularcommunication interface, this disclosure contemplates any suitablecommunication interface.

In particular embodiments, bus 512 includes hardware, software, or bothcoupling components of computer system 500 to each other. As an exampleand not by way of limitation, bus 512 may include an AcceleratedGraphics Port (AGP) or other graphics bus, an Enhanced Industry StandardArchitecture (EISA) bus, a front-side bus (FSB), a HYPERTRANSPORT (HT)interconnect, an Industry Standard Architecture (ISA) bus, an INFINIBANDinterconnect, a low-pin-count (LPC) bus, a memory bus, a Micro ChannelArchitecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, aPCI-Express (PCI-X) bus, a serial advanced technology attachment (SATA)bus, a Video Electronics Standards Association local (VLB) bus, oranother suitable bus or a combination of two or more of these. Bus 512may include one or more buses 512, where appropriate. Although thisdisclosure describes and illustrates a particular bus, this disclosurecontemplates any suitable bus or interconnect.

Herein, reference to a computer-readable storage medium encompasses oneor more non-transitory, tangible computer-readable storage mediapossessing structure. As an example and not by way of limitation, acomputer-readable storage medium may include a semiconductor-based orother integrated circuit (IC) (such, as for example, afield-programmable gate array (FPGA) or an application-specific IC(ASIC)), a hard disk, an HDD, a hybrid hard drive (HHD), an opticaldisc, an optical disc drive (ODD), a magneto-optical disc, amagneto-optical drive, a floppy disk, a floppy disk drive (FDD),magnetic tape, a holographic storage medium, a solid-state drive (SSD),a RAM-drive, a SECURE DIGITAL card, a SECURE DIGITAL drive, or anothersuitable computer-readable storage medium or a combination of two ormore of these, where appropriate. Herein, reference to acomputer-readable storage medium excludes any medium that is noteligible for patent protection under 35 U.S.C. §101. Herein, referenceto a computer-readable storage medium excludes transitory forms ofsignal transmission (such as a propagating electrical or electromagneticsignal per se) to the extent that they are not eligible for patentprotection under 35 U.S.C. §101. A computer-readable non-transitorystorage medium may be volatile, non-volatile, or a combination ofvolatile and non-volatile, where appropriate.

This disclosure contemplates one or more computer-readable storage mediaimplementing any suitable storage. In particular embodiments, acomputer-readable storage medium implements one or more portions ofprocessor 502 (such as, for example, one or more internal registers orcaches), one or more portions of memory 504, one or more portions ofstorage 506, or a combination of these, where appropriate. In particularembodiments, a computer-readable storage medium implements RAM or ROM.In particular embodiments, a computer-readable storage medium implementsvolatile or persistent memory. In particular embodiments, one or morecomputer-readable storage media embody software. Herein, reference tosoftware may encompass one or more applications, bytecode, one or morecomputer programs, one or more executables, one or more instructions,logic, machine code, one or more scripts, or source code, and viceversa, where appropriate. In particular embodiments, software includesone or more application programming interfaces (APIs). This disclosurecontemplates any suitable software written or otherwise expressed in anysuitable programming language or combination of programming languages.In particular embodiments, software is expressed as source code orobject code. In particular embodiments, software is expressed in ahigher-level programming language, such as, for example, C, Perl, or asuitable extension thereof. In particular embodiments, software isexpressed in a lower-level programming language, such as assemblylanguage (or machine code). In particular embodiments, software isexpressed in JAVA. In particular embodiments, software is expressed inHyper Text Markup Language (HTML), Extensible Markup Language (XML), orother suitable markup language.

Although the present invention has been described with severalembodiments, a myriad of changes, variations, alterations,transformations, and modifications may be suggested to one skilled inthe art, and it is intended that the present invention encompass suchchanges, variations, alterations, transformations, and modifications asfall within the scope of the appended claims.

What is claimed is:
 1. A method comprising, by an event managementsystem: receiving, by a check-in device associated with event managementsystem, a ticket identifier for an attendee of an event, the check-indevice comprising an access point, the access point being operable toconnect by a wireless signal to one or more mobile devices;transmitting, from the check-in device to a gatekeeper system associatedwith the event management system, the ticket identifier for theattendee, wherein the gatekeeper system comprises a router, a switch,and a computing system, and wherein the check-in device is communicablyconnected to the gatekeeper system; validating, by the gatekeepersystem, the ticket identifier for the attendee; and transmitting, fromthe gatekeeper system to the check-in device, an indication of validityof the ticket identifier for the attendee.
 2. The method of claim 1,further comprising: initiating, by the check-in device, receiving of theticket identifier from a mobile device of the attendee; receiving, bythe check-in device, the ticket identifier from the mobile device of theattendee; transmitting, from the check-in device to the gatekeepersystem via a wireless connection signal, the ticket identifier;receiving, by the check-in device from the gatekeeper system via thewireless connection signal, the indication of validity of the ticketidentifier; and displaying, by the check-in device, the indication ofvalidity of the ticket identifier.
 3. The method of claim 2, furthercomprising: transmitting, from the check-in device to the gatekeepersystem via the wireless connection signal, a request to update a ticketinformation to identify that the attendee associated with the ticketidentifier is checked-in.
 4. The method of claim 1, wherein thegatekeeper system comprises a portable, ruggedized, and waterproof casethat substantially encloses a router and a switch.
 5. The method ofclaim 1, wherein each check-in device is substantially enclosed by aportable, ruggedized, and waterproof case.
 6. The method of claim 1,wherein the check-in device is coupled to the access point and a supportstructure.
 7. The method of claim 1, further comprising: receiving, bythe gatekeeper system from the check-in device via a wireless connectionsignal, a ticket identifier received from a mobile device of theattendee; comparing, by the gatekeeper system, the ticket identifier toa stored ticket information; generating, by the gatekeeper system, anindication of validity of the ticket based on the comparison; andtransmitting, by the gatekeeper system to the check-in device via thewireless connection signal, the indication of validity of the ticketidentifier.
 8. The method of claim 7, further comprising: updating, bythe gatekeeper system, the stored ticket information based on thecomparison.
 9. The method of claim 7, further comprising: receiving, bythe gatekeeper system from the check-in device via the wirelessconnection signal, one or more status indicators; and displaying, by thegatekeeper system, indicator information based on the one or more statusindicators.
 10. The method of claim 7, further comprising: accessing, bythe gatekeeper system from the event management system, a first ticketinformation identifying, for each of a plurality of attendees of theevent: a ticket identifier associated with the attendee; and whether theattendee is checked-in or not checked-in.
 11. The method of claim 7,further comprising: transmitting, by the gatekeeper system, a ticketindication message configured to cause the event management system toupdate a master ticket information.
 12. The method of claim 7, furthercomprising: receiving, by the gatekeeper system, an update messageincluding an indication of one or more changes to a master ticketinformation; and updating, by the gatekeeper system, the stored ticketinformation based on the update message to match the master ticketinformation.
 13. The method of claim 1, wherein the computing systemcomprises a server of the event management system.
 14. The method ofclaim 1, wherein the gatekeeper system is present on-site at the event.15. The method of claim 14, wherein the check-in device is communicablyconnected to the gatekeeper system via a wireless connection signal. 16.The method of claim 14, wherein the check-in device is communicablyconnected to the gatekeeper system via a switch connector to the switch.17. The method of claim 1, wherein the gatekeeper system is locatedoff-site from the event.
 18. The method of claim 17, wherein thegatekeeper system is communicably connected to the check-in device via awireless connection signal.
 19. One or more computer-readablenon-transitory storage media embodying software that is operable whenexecuted by an event management system to: receive, by a check-in deviceassociated with the event management system, a ticket identifier for anattendee of an event, the check-in device comprising an access point,the access point being operable to connect by a wireless signal to oneor more mobile devices; transmit, from the check-in device to agatekeeper system associated with the event management system, theticket identifier for the attendee, wherein the gatekeeper systemcomprises a router, a switch, and a computing system, and wherein thecheck-in device is communicably connected to the gatekeeper system;validate, by the gatekeeper system, the ticket identifier for theattendee; and transmit, from the gatekeeper system to the check-indevice, an indication of validity of the ticket identifier for theattendee.
 20. An event management system comprising: one or moreprocessors; and a memory coupled to the processors comprisinginstructions executable by the processors, the processors being operablewhen executing the instructions to: receive, by a check-in deviceassociated with the event management system, a ticket identifier for anattendee of an event, the check-in device comprising an access point,the access point being operable to connect by a wireless signal to oneor more mobile devices; transmit, from the check-in device to agatekeeper system associated with the event management system, theticket identifier for the attendee, wherein the gatekeeper systemcomprises a router, a switch, and a computing system, and wherein thecheck-in device is communicably connected to the gatekeeper system;validate, by the gatekeeper system, the ticket identifier for theattendee; and transmit, from the gatekeeper system to the check-indevice, an indication of validity of the ticket identifier for theattendee.